═══ 1. ScreenSaver Installation Program ═══ Use the Source directory entry field to set the directory from which ScreenSaver is to be installed. Default is the current directory and there should be no need to change this. Use the Destination directory entry field to set the directory into which ScreenSaver is to be installed. Default is the current directory (except when this is on a diskette). You can change this to any drive and directory you want. Use the Destination directory for DLLs entry field to set the directory into which the EMX runtime DLLs (i.e. the files which contain the runtime library for the EMX/GCC compiler, with which ScreenSaver was compiled) are to be installed. These DLLs are required by many OS/2 programs and therefore should be installed to a directory in your LIBPATH where they are found by these programs. Default is the \OS2\DLL directory on your boot drive. Change this to any directory you want, but make sure this directory can be found in the LIBPATH statement in your CONFIG.SYS file. It is possible that there is more than one set of these DLLs installed on your computer. Only one set of the DLLs is required system wide. You can delete all but the newest set. Attention! If there are any programs running that use existing EMX DLLs on your hard disk, you have to stop them or installation will fail. Alternatively choose another DLL destination directory. If you have an older version of ScreenSaver running, shut it down before trying to install. It may even be necessary to reboot your computer, because OS/2 may have locked the ScreenSaver file SSDLL.DLL (this can happen even if ScreenSaver has been stopped). If the Create WPS object box is checked, a program object is created. If the Create in startup folder box is checked, too, this object is created in the OS/2 System Startup folder, so ScreenSaver will be started automatically at system startup. Use the Install Win-OS/2 fullscreen support check box to choose if you want ScreenSaver to be activated from Win-OS/2 fullscreen sessions. If you choose to install this option, a Windows screen saver is installed in your Win-OS/2 directory. Use the Win-OS/2 "Control Panel" to set its timeout. Please set the directory where Win-OS/2 is installed in the Win-OS/2 directory entry field. Use the Install DOS fullscreen support check box to choose if you want ScreenSaver to be activated from DOS fullscreen sessions. If you choose to install this option, a DOS screen saver is installed in your OS/2 DOS directory (\OS2\MDOS). It is invoked from the AUTOEXEC.BAT file of your OS/2 boot drive. Set the timeout parameter in the AUTOEXEC.BAT file; for example "SSDKICK 10" sets the timeout for DOS fullscreen sessions to 10 minutes. The default timeout is 5 minutes. To disable the DOS saver, set timeout to 0. ═══ 2. ScreenSaver Installation Notes ═══ IMPORTANT INFORMATION. PLEASE READ!  If you use OS/2 2.x, make sure there is a dot (".") in the LIBPATH statement in your CONFIG.SYS file (this is default in Warp).  If DPMS switching hangs your computer, try changing the BIOS power management settings; see ScreenSaver online help topic "Green monitor support".  ScreenSaver is Shareware. Some functions are available only to registered users. See online help or the file REGISTER.DOC for how to register.  ScreenSaver provides password protection. For the pre-set password, see online help. Please note that this password is case sensitive! If you have the impression that the system is not unlocked although you typed in the correct password, please check if Caps Lock is active.  There exists a little utility called SSKICK which starts a module when executed. You can add this utility to the Desktop menu (see online help).  For available command line switches, see online help.  In this distribution, I have included foreign modules. For copyright information see the README file.  A few users have reported problems with some Deskpic modules. If a Deskpic module crashes on your system, delete the corresponding *.DSS file.  Please read the online help topic on "low priority" if saver animation is not smooth enough. ═══ 3. Notes for CID installations ═══  Overview - The installation program can be controlled by command line parameters and can run completely unattended. This makes installation over a network much easier. - All settings which the user normally uses in the installation program are accessible through command line parameters. If a command line parameter is not given, a default value will be used (see below). - There are some additional parameters, for example to exclude some files from being installed (if you want to spare certain modules). - Installation can be done without any user interaction. A server can start the installation program on a client and is notified of success or failure by the return code of the installation program. In case of this unattended installation, the installation program does not expect user input, does not output error messages (except through its return code), and ends itself automatically after installation. A log file can be created.  Return codes of the installation program 0 - installation successful 1 - internal problem 2 - installation cancelled 3 - installation failed  Command line parameters Notes: - Command line parameters are not case-sensitive. - If a parameter is not given, the installation program will choose a default value (see below). If you don't give any parameters at all, the installation program acts like in prior versions (<= 2.4). - Instead of TRUE you can write YES, instead of FALSE you can write NO. - There must not be a space after the '=' character. The value must follow immediately (see examples). - The EXCLUDEFILES parameter must be the last parameter. Supported command line parameters: destpath= Description: Directory where ScreenSaver will be installed to Value: Path Default: The current directory (except if the current directory is on a diskette drive, in this case another directory is chosen) destpathdll= Description: Directory where the EMX-DLLs will be copied to Value: Path Default: x:\OS2\DLL (x is the OS/2 boot drive) sourcepath= Description: Source path where the files to be installed can be found Value: Path Default: Current directory winos2path= Description: Windows directory Value: Path Default: x:\OS2\MDOS\WINOS2 or the \WINDOWS directory on the first drive (C..Z) where it exists targetfolder= Description: Folder where the ScreenSaver WPS object will be created Value: Any valid folder name Default: "" createobject= Description: Create WPS object yes/no Value: TRUE or FALSE Default: TRUE cmdline= Description: Command line for ScreenSaver (will be set as parameter in the WPS program object). Please note that you have to enclose the cmdline= parameter and its argument in double quotes if the argument contains any space characters, i.e. you have to write install "cmdline=-I SSAVER.INI" to get "-I SSAVER.INI" as the command line for the WPS object. Value: Any valid command line, e.g. "-I SSAVER.INI" Default: No command line installwinos2= Description: Install WinOS/2 fullscreen support yes/no Value: TRUE or FALSE Default: TRUE installdos= Description: Install DOS fullscreen support yes/no Value: TRUE or FALSE Default: TRUE unattendedinstallation= Description: The installation program will run without user input and will end itself when installation is done Value: TRUE or FALSE Default: FALSE logfile= Description: All messages the installation program shows to the user (and some other useful information) can be logged to a log file. If the given file already exists, the log information will be appended. Value: File name ( including path) Default: No log file is created extpasswordfile= Description: The "external password file" which will be used by ScreenSaver can be set already at installation time. The given path will be written to the OS2.INI file by the installation program. If ScreenSaver is started with the -I or -i parameter, the settings will be read from the given INI file instead of OS2.INI and the extpasswordfile= setting will have no effect. Value: Path Default: No external password file is set os2drive= Description: OS/2 boot drive. If you install from a server to a workstation and want to run the installation program on the server itself, you may need to set the boot drive of the workstation. If you run the installation program on the server, you will not be able to create a WPS object on the workstation. Installing this way is not recommended. Value: Drive letter (C..Z) Default: The drive which is reported as boot drive by OS/2 excludefiles Description: To exclude certain modules from installation, just list their file names here. This has to be the last parameter. Value: List of files which should not be copied. Seperate the single file names with spaces. There can be any number of files listed. Default: All files are copied, no files are excluded.  Examples install unattendedinstallation=true logfile=s:\install.log targetfolder="" cmdline="-t" install os2drive=y destpath=y:\ssaver installdos=false installwinos2=false createobject=false install winos2path=z:\win31 excludefiles trek1.dss flame.ssm 3d.ssm puzzle.ssm  Notes - The DOS fullscreen support file (SSDKICK.COM) is copied to the directory x:\OS2\MDOS and the line "x:\OS2\MDOS\SSDKICK.COM 5" is inserted into the x:\AUTOEXEC.BAT file. - The Win-OS/2 fullscreen support file (SSWKICK.SCR) is copied to the Windows directory and the line "SCRNSAVE.EXE=w:\windowspath\sswkick.scr" is added to the [boot] section of the SYSTEM.INI file. - If fullscreen support for a session type is not installed, the above changes are not made and the files are not copied.  List of modules To exclude a module from installation, just list its file name after the EXCLUDEFILES parameter. file name: module name: Deskpic modules: ACIDRAIN.DSS Acid Rain [Deskpic] AQUARIUM.DSS Aquarium [Deskpic] BLOCKS.DSS Blocks [Deskpic] BOUNCE.DSS Bounce [Deskpic] BUSYBEES.DSS BusyBees [Deskpic] CLOCK.DSS Clock [Deskpic] EYES.DSS Eyes [Deskpic] FIRE.DSS Fireworks [Deskpic] FLASH.DSS Flashlight [Deskpic] KALSCOPE.DSS Kaleidoscope [Deskpic] MELT.DSS Melting screen [Deskpic] NEWPOLY.DSS Fading Polygons [Deskpic] OS22BOUN.DSS OS/2 v2.0 Bounce [Deskpic] OS2BOUNC.DSS OS/2 Bounce [Deskpic] POLYGONS.DSS Polygons [Deskpic] PUZZLE.DSS Puzzle [Deskpic] PUZZLE2.DSS The Puzzle II [Deskpic] RADAR.DSS Radar [Deskpic] RAIN.DSS Rain [Deskpic] SHRINK.DSS The Shrink [Deskpic] SMARTIES.DSS Smarties [Deskpic] SPHERES.DSS Spheres [Deskpic] SPLINES.DSS Splines [Deskpic] STRING.DSS String [Deskpic] SWARM.DSS Swarm [Deskpic] TREK1.DSS Star Trek 1 [Deskpic] WALL.DSS Wallpaper [Deskpic] WORM.DSS Worm [Deskpic] ScreenSaver modules: 3D.SSM 3 Dimensions BANNER.SSM Banner BITMAP.SSM Bitmap BLANK.SSM Blank CLOCK.SSM Clock COLORS.SSM Colors DIMMER.SSM Dimmer FADE.SSM Fade To Black FLAME.SSM Flame FORTUNES.SSM Fortunes HOPALONG.SSM Hopalong ICON.SSM Icon Spiral IMAGE.SSM Image IRONMAID.SSM Iron Maiden LENSE.SSM Lense LIFE.SSM Life LINES.SSM Lines MEALSTRM.SSM Mealstorm OVERTIME.SSM Working Overtime PUZZLE.SSM Puzzle PYRAMIDS.SSM Pyramids PYRO.SSM Pyro QIX.SSM Qix ROTOR.SSM Rotor SLIDES.SSM Slideshow SPOT.SSM Spot STARS.SSM Starflight SWARM.SSM Swarm WORM.SSM Worm ═══ 4. Uninstalling ScreenSaver ═══ If you want to completely remove ScreenSaver, do the following: 1. Exit ScreenSaver (choose Close from the window list) 2. Delete the file SSWKICK.SCR from your windows directory 3. Delete the file SSDKICK.COM from the \OS2\MDOS directory 4. Remove the line "\OS2\MDOS\SSDKICK x" from your AUTOEXEC.BAT file 5. Remove the program object from the OS/2 startup folder 6. Delete all the files in the SSAVER directory 7. If deleting all files fails (OS/2 may have locked some files), reboot and try again to delete all files in the SSAVER directory 8. Remove the SSAVER directory